Welcome back for a few tips on file names.
Some older computer operating systems place a lot of restrictions on file names,
for example, early versions of Windows only allowed eight characters
before the period and three after the period.
Modern computer operating systems have fewer restrictions on your file names.
Still, it's a good idea for maximum portability of your files between
computers to place a few restrictions on yourself.
Here are our suggestions.
First of all, don't use commas in a file name.
So don't say, Olympics, winter.
Don't make that be a file name even if your computer operating system allows it.
Don't use more than one period like .txt.3.csv.
Don't do that.
Don't use a forward slash or a backward slash in your file name.
No Olympic/winter.
That's usually the convention for making subdirectories.
You don't want to have a slash in your file name or
a backslash in your file name.
Don't use spaces even though most operating systems will permit that now.
Olympic space winter, also not a good idea.
Do follow some conventions for what happens after the period.
.txt should be for plain text.
.py, if you've got a file that's Python code.
.csv, if you've got text that's in the comma separated values format.
So we've actually been bad here, we've got this file olympics.txt,
it really should have been olympics.csv.
Another file ending is .xls.
That's for files that are in a Microsoft Excel format.
.doc or .docx for things that are in Microsoft Word format.
The reason for following these conventions about what goes after the period,
is that computer operating systems will usually look at that extension,
the .txt or the .csv, or the .py.
If you just double click on the file they'll decide which program to open.
So if it's a .py file they'll try to open it in a text editor or
they'll try to execute it as a Python program.
If you have a .xls, it'll try to open it in Microsoft Excel and so on.
So that's all for now, just a few words on naming conventions for your files.
I'll see you next time.